Bump guava from 23.6-jre to 32.0.0-jre in /samples/languages/java/label_image#1
Conversation
Bumps [guava](https://github.com/google/guava) from 23.6-jre to 32.0.0-jre. - [Release notes](https://github.com/google/guava/releases) - [Commits](https://github.com/google/guava/commits) --- updated-dependencies: - dependency-name: com.google.guava:guava dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Rule: avoid pickle
Severity:
File: research/steve/replay.py
Lines: 108 - 108
Scanner: SEMGREP
More Info
Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format.</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: tutorials/image/cifar10_estimator/generate_cifar10_tfrecords.py<br>
<b style="color:black">Lines</b>: 68 - 68<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: tutorials/image/cifar10_estimator/generate_cifar10_tfrecords.py<br>
<b style="color:black">Lines</b>: 70 - 70<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/rebar/datasets.py<br>
<b style="color:black">Lines</b>: 55 - 55<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/rebar/download_data.py<br>
<b style="color:black">Lines</b>: 82 - 82<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/steve/replay.py<br>
<b style="color:black">Lines</b>: 78 - 78<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/steve/replay.py<br>
<b style="color:black">Lines</b>: 104 - 104<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/steve/replay.py<br>
<b style="color:black">Lines</b>: 105 - 105<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/steve/replay.py<br>
<b style="color:black">Lines</b>: 106 - 106<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/steve/replay.py<br>
<b style="color:black">Lines</b>: 107 - 107<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: official/recommendation/data_preprocessing.py<br>
<b style="color:black">Lines</b>: 87 - 87<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: official/recommendation/data_preprocessing.py<br>
<b style="color:black">Lines</b>: 174 - 174<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/fivo/fivo/data/calculate_pianoroll_mean.py<br>
<b style="color:black">Lines</b>: 53 - 53<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/fivo/fivo/data/calculate_pianoroll_mean.py<br>
<b style="color:black">Lines</b>: 61 - 61<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/fivo/fivo/data/datasets.py<br>
<b style="color:black">Lines</b>: 186 - 186<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/fivo/fivo/data/datasets_test.py<br>
<b style="color:black">Lines</b>: 98 - 98<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/fivo/fivo/data/datasets_test.py<br>
<b style="color:black">Lines</b>: 157 - 157<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/learning_to_remember_rare_events/data_utils.py<br>
<b style="color:black">Lines</b>: 58 - 58<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/learning_to_remember_rare_events/data_utils.py<br>
<b style="color:black">Lines</b>: 60 - 60<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/learning_to_remember_rare_events/data_utils.py<br>
<b style="color:black">Lines</b>: 180 - 180<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/lm_commonsense/eval.py<br>
<b style="color:black">Lines</b>: 144 - 144<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/lm_commonsense/eval.py<br>
<b style="color:black">Lines</b>: 168 - 168<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/pcl_rl/controller.py<br>
<b style="color:black">Lines</b>: 241 - 241<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/pcl_rl/expert_paths.py<br>
<b style="color:black">Lines</b>: 39 - 39<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: eval detected<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/neural_gpu/program_utils.py<br>
<b style="color:black">Lines</b>: 342 - 342<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Detected the use of eval(). eval() can be dangerous if used to evaluate
dynamic content. If this content can be input from outside the program, this
may be a code injection vulnerability. Ensure evaluated content is not definable
by external sources.
</details><p><b style="color:black" >Rule</b>: eval detected<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/rebar/rebar_train.py<br>
<b style="color:black">Lines</b>: 156 - 156<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Detected the use of eval(). eval() can be dangerous if used to evaluate
dynamic content. If this content can be input from outside the program, this
may be a code injection vulnerability. Ensure evaluated content is not definable
by external sources.
</details><p><b style="color:black" >Rule</b>: eval detected<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/rebar/rebar_train.py<br>
<b style="color:black">Lines</b>: 157 - 157<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Detected the use of eval(). eval() can be dangerous if used to evaluate
dynamic content. If this content can be input from outside the program, this
may be a code injection vulnerability. Ensure evaluated content is not definable
by external sources.
</details><p><b style="color:black" >Rule</b>: exec command detected<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: official/vision/image_classification/common.py<br>
<b style="color:black">Lines</b>: 448 - 449<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Detected the use of exec(). exec() can be dangerous if used to evaluate
dynamic content. If this content can be input from outside the program, this
may be a code injection vulnerability. Ensure evaluated content is not definable
by external sources.
</details><p><b style="color:black" >Rule</b>: exec command detected<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/neural_gpu/program_utils.py<br>
<b style="color:black">Lines</b>: 184 - 184<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Detected the use of exec(). exec() can be dangerous if used to evaluate
dynamic content. If this content can be input from outside the program, this
may be a code injection vulnerability. Ensure evaluated content is not definable
by external sources.
</details><p><b style="color:black" >Rule</b>: exec command detected<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/neural_gpu/program_utils.py<br>
<b style="color:black">Lines</b>: 297 - 297<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Detected the use of exec(). exec() can be dangerous if used to evaluate
dynamic content. If this content can be input from outside the program, this
may be a code injection vulnerability. Ensure evaluated content is not definable
by external sources.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: official/utils/logs/mlperf_helper.py<br>
<b style="color:black">Lines</b>: 181 - 183<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/single_task/run_eval_tasks.py<br>
<b style="color:black">Lines</b>: 176 - 176<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/efficient-hrl/scripts/local_eval.py<br>
<b style="color:black">Lines</b>: 72 - 72<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/efficient-hrl/scripts/local_train.py<br>
<b style="color:black">Lines</b>: 72 - 72<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/learning_to_remember_rare_events/data_utils.py<br>
<b style="color:black">Lines</b>: 193 - 193<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/learning_to_remember_rare_events/data_utils.py<br>
<b style="color:black">Lines</b>: 201 - 202<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/learning_to_remember_rare_events/data_utils.py<br>
<b style="color:black">Lines</b>: 210 - 211<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/webcam.py<br>
<b style="color:black">Lines</b>: 385 - 385<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/webcam.py<br>
<b style="color:black">Lines</b>: 390 - 390<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: subprocess shell equals true<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/webcam.py<br>
<b style="color:black">Lines</b>: 423 - 423<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found 'subprocess' function '$FUNC' with 'shell=True'. This is dangerous because this call will spawn
the command using a shell process. Doing so propagates current shell settings and variables, which
makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/autoaugment/data_utils.py<br>
<b style="color:black">Lines</b>: 182 - 182<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/common/utils.py<br>
<b style="color:black">Lines</b>: 386 - 386<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/common/utils.py<br>
<b style="color:black">Lines</b>: 556 - 556<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/single_task/ga_train.py<br>
<b style="color:black">Lines</b>: 73 - 73<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/single_task/ga_train.py<br>
<b style="color:black">Lines</b>: 90 - 90<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/single_task/pg_train.py<br>
<b style="color:black">Lines</b>: 290 - 290<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/brain_coder/single_task/pg_train.py<br>
<b style="color:black">Lines</b>: 412 - 412<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/cognitive_mapping_and_planning/src/utils.py<br>
<b style="color:black">Lines</b>: 117 - 117<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/cognitive_mapping_and_planning/src/utils.py<br>
<b style="color:black">Lines</b>: 122 - 122<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/cvt_text/base/utils.py<br>
<b style="color:black">Lines</b>: 44 - 44<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/cvt_text/base/utils.py<br>
<b style="color:black">Lines</b>: 55 - 55<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/rebar/datasets.py<br>
<b style="color:black">Lines</b>: 55 - 55<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/rebar/download_data.py<br>
<b style="color:black">Lines</b>: 82 - 82<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/slim/datasets/download_and_convert_cifar10.py<br>
<b style="color:black">Lines</b>: 77 - 77<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid cPickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/slim/datasets/download_and_convert_cifar10.py<br>
<b style="color:black">Lines</b>: 79 - 79<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `cPickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: official/nlp/xlnet/preprocess_squad_data.py<br>
<b style="color:black">Lines</b>: 132 - 132<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: avoid pickle<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: official/nlp/xlnet/run_squad.py<br>
<b style="color:black">Lines</b>: 284 - 284<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Avoid using `pickle`, which is known to lead to code execution vulnerabilities.
When unpickling, the serialized data could be manipulated to run arbitrary code.
Instead, consider serializing the relevant data as JSON or a similar text-based
serialization format.
</details><p><b style="color:black" >Rule</b>: dangerous system call<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/cognitive_planning/viz_active_vision_dataset_main.py<br>
<b style="color:black">Lines</b>: 269 - 274<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability.
</details><p><b style="color:black" >Rule</b>: dangerous system call<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/images_to_videos.py<br>
<b style="color:black">Lines</b>: 55 - 55<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability.
</details><p><b style="color:black" >Rule</b>: dangerous system call<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/images_to_videos.py<br>
<b style="color:black">Lines</b>: 61 - 69<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability.
</details><p><b style="color:black" >Rule</b>: dangerous system call<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/webcam.py<br>
<b style="color:black">Lines</b>: 288 - 288<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability.
</details><p><b style="color:black" >Rule</b>: dangerous system call<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/dataset/webcam.py<br>
<b style="color:black">Lines</b>: 300 - 308<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability.
</details><p><b style="color:black" >Rule</b>: dangerous system call<br>
<b style="color:black" >Severity</b>: <img src="https://cidersecurity-public-icons.s3.amazonaws.com/prSeverityIcons/critical.svg" alt="CRITICAL" width="62px" align="center"><br><b style="color:black">File</b>: research/tcn/utils/util.py<br>
<b style="color:black">Lines</b>: 200 - 200<br>
<b style="color:black" >Scanner:</b> <a href="https://semgrep.dev/">SEMGREP</a></p>
<details>
<summary><b style="color:black">More Info</b></summary>
Found dynamic content used in a system call. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Use the 'subprocess' module instead, which is easier to use without accidentally exposing a command injection vulnerability.
</details>
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Rule: 26-GENERIC-PASSWORD
Severity:
File: research/cvt_text/corpus_processing/unlabeled_data.py
Lines: 31
Scanner: Secret Diver
More Info
Contains PASSWORDRule: 26-GENERIC-PASSWORD
Severity:
File: research/qa_kg/exp_1_hop/test.py
Lines: 47
Scanner: Secret Diver
More Info
Contains PASSWORDRule: 26-GENERIC-PASSWORD
Severity:
File: research/qa_kg/exp_1_hop/train_gt_layout.py
Lines: 47
Scanner: Secret Diver
More Info
Contains PASSWORDRule: 26-GENERIC-PASSWORD
Severity:
File: research/qa_kg/util/data_reader.py
Lines: 155
Scanner: Secret Diver
Bumps guava from 23.6-jre to 32.0.0-jre.
Release notes
Sourced from guava's releases.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.